View MMK2-67025EV-45QM_6941234.PDF datasheet online --- IC-ON-LINE

Datasheet File OCR Text:

m67025e rev. f june 30, 1999 1 introduction the m67025e is a very low power cmos dual port static ram organised as 8192 16. the m67025e is designed to be used as a stand-alone 16 bit dual port ram or as a combination master/slave dual port for 32 bit or more width systems. the temic master/slave dual port approach in memory system applications results in full speed, error free operation without the need of an additional discrete logic. master and slave devices provide two independant ports with separate control, address and i/o pins that permit independant, asynchronous access for reads and writes to any location in the memory. an automatic power down feature controlled by cs permits the on-chip circuitry of each port in order to enter a very low stand by power mode. using an array of eight transistors (8t) memory cell, the m67025e combines an extremely low standby supply current (typ = 1.0 m a) with a fast access time at 30 ns over the full temperature range. all versions offer battery backup data retention capability with a typical power consumption at less than 5 m w. the m67025e is processed according to the methods of the latest revision of the mil std 883 (class b or s), esa scc 9000 or qml. features fast access time : 30, 45 ns wide temperature range : 55 c to +125 c separate upper byte and lower byte control for multiplexed bus compatibility expandable data bus to 32 bits or more using master/slave chip select when using more than one device on chip arbitration logic versatile pin select for master or slave : m/s = h for busy output flag on master m/s = l for busy input flag on slave int flag for port to port communication full hardware support of semaphore signaling between ports fully asynchronous operation from either port battery back-up operation : 2 v data retention ttl compatible single 5 v 10 % power supply 8 k 16 cmos dual port ram rad tolerant
m67025e rev. f june 30, 1999 2 interface block diagram note : 1. (master) : busy is output. (slave) : busy is input. 2. lb = lower byte ub = upper byte pin names left port right port names cs l cs r chip select r/w l r/w r read/write enable oe l oe r output enable a 0l 12l a 0r 12r address i/o 0l 15l i/o 0r 15r data input/output sem l sem r semaphore enable ub l ub r upper byte select lb l lb r lower byte select int l int r interrupt flag busy l busy r busy flag m/s master or slave select vcc power gnd ground
m67025e rev. f june 30, 1999 3 functional description pin configuration 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 63 62 61 60 59 58 57 56 55 54 53 52 51 50 49 48 47 46 45 44 43 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 67025 84-pin mqfpf top view index a 7l a 6l a 5l a 4l a 3l a 2l a 1l a 0l int l busy l gnd m/s busy r int r a 0r a 1r a 2r a 3r a 4r a 5r a 6r i/o 8l i/o 9l i/o 10l i/o 11l i/o 12l i/o 13l gnd i/o 14l i/o 15l vcc gnd i/o 0r i/o 1r i/o 2r vcc i/o 3r i/o 4r i/o 5r i/o 6r i/o 7r i/o 8r i/o i/o i/o i/o i/o i/o gnd i/o i/o oe vcc r/w sem ce ub lb a a a a 7l 6l 5l 4l 3l 2l 1l 0l l l l l l l 11l 10l 9l 8l i/o i/o i/o i/o i/o i/o gnd i/o oe r/w gnd sem ce ub lb a a a a 9r 10r 11r 12r 13r 14r 15r r r r r r r 10r 9r 8r 7r a 11r a 12r 12l a
m67025e rev. f june 30, 1999 4 functional description the m67025e has two ports with separate control, address and i/0 pins that permit independent read/write access to any memory location. these devices have an automatic power-down feature controlled by cs .cs controls on-chip power-down circuitry which causes the port concerned to go into stand-by mode when not selected (cs high). when a port is selected access to the full memory array is permitted. each port has its own output enable control (oe ). in read mode, the port's oe turns the output drivers on when set low. non-conflicting read/write conditions are illustrated in table 1. the interrupt flag (int ) allows communication between ports or systems. if the user chooses to use the interrupt function, a memory location (mail box or message center) is assigned to each port. the left port interrupt flag (int l ) is set when the right port writes to memory location 1ffe (hex). the left port clears the interrupt by reading address location 1ffe. similarly, the right port interrupt flag (int r ) is set when the left port writes to memory location 1fff (hex), and the right port must read memory location 1fff in order to clear the interrupt flag (int r ). the 16 bit message at 1ffe or 1fff is user-defined. if the interrupt function is not used, address locations 1ffe and 1fff are not reserved for mail boxes but become part of the ram. see table 3 for the interrupt function. arbitration logic functional description the arbitration logic will resolve an address match or a chip select match down to a minimum of 5 ns determine which port has access. in all cases, an active busy flag will be set for the inhibited port. the busy flags are required when both ports attempt to access the same location simultaneously. should this conflict arise, on-chip arbitration logic will determine which port has access and set the busy flag for the inhibited port. busy is set at speeds that allow the processor to hold the operation with its associated address and data. it should be noted that the operation is invalid for the port for which busy is set low. the inhibited port will be given access when busy goes inactive. a conflict will occur when both left and right ports are active and the two addresses coincide. the on-chip arbitration determines access in these circumstances. two modes of arbitration are provided : (1) if the addresses match and are valid before cs on-chip control logic arbitrates between cs l and cs r for access ; or (2) if the cs s are low before an address match, on-chip control logic arbitrates between the left and right addresses for access (refer to table 4). the inhibited port's busy flag is set and will reset when the port granted access completes its operation in both arbitration modes. data bus width expansion master/slave description expanding the data bus width to 32 or more bits in a dual-port ram system means that several chips may be active simultaneously. if every chips has a hardware arbitrator, and the addresses for each arrive at the same time one chip may activate in l busy signal while another activates its r busy signal. both sides are now busy and the cpus will wait indefinitely for their port to become free. to overcome this abusy lock-outo problem, mhs has developped a master/slave system which uses a single hardware arbitrator located on the master. the slave has busy inputs which allow direct interface to the master with no external components, giving a speed advantage over other systems. when dual-port rams are expanded in width, the slave rams must be prevented from writing until after the busy input has settled. otherwise, the slave chip may begin a write cycle during a conflict situation. conversely, the write pulse must extend a hold time beyond busy to ensure that a write cycle occurs once the conflict is resolved. this timing is inherent in all dual-port memory systems where more than one chip is active at the same time. the write pulse to the slave must be inhibited by the master's maximum arbitration time. if a conflict then occurs, the write to the slave will be inhibited because of the master's busy signal. semaphore logic functional description the m67025e is an extremely fast dual-port 4k 16 cmos static ram with an additional locations dedicated to binary semaphore flags. these flags allow either of the processors on the left or right side of the dual-port ram to claim priority over the other for functions defined by the system software. for example, the semaphore flag can be used by oner processor to inhibit the other from accessing a portion of the dual-port ram or any other shared resource.
m67025e rev. f june 30, 1999 5 the dual-port ram has a fast access time, and the two ports are completely independent of each another. this means that the activity on the left port cannot slow the access time of the right port. the ports are identical in function to standard cmos static rams and can be read from, or written to, at the same time with the only possible conflict arising from simultaneous writing to, or a simultaneous read/write operation on, a non-semaphore location. semaphores are protected against such ambiguous situations and may be used by the system program to prevent conflicts in the non-semaphore segment of the dual-port ram. the devices have an automatic power-down feature controlled by cs , the dual-port ram select and sem , the semaphore enable. the cs and sem pins control on-chip-power-down circuitry that permits the port concerned to go into stand-by mode when not selected. this conditions is shown in table 1 where cs and sem are both high. systems best able to exploit the m67025e are based around multiple processors or controllers and are typically very high-speed, software controlled or software-intensive systems. these systems can benefit from the performance enhancement offered by the m 67025 hardware semaphores, which provide a lock-out mechanism without the need for complex programming. software handshaking between processors offers the maximum level of system flexibility by permitting shared resources to be allocated in varying configurations. the m67025e does not use its semaphore flags to control any resources through hardware, thus allowing the system designer total flexibility in system architecture. an advantage of using semaphores rather than the more usual methods of hardware arbitration is that neither processor ever incurs wait states. this can prove to be a considerable advantage in very high speed systems. how the semaphore flags work the semaphore logic is a set of eight latches independent of the dual-port ram. these latches can be used to pass a flag or token, from one port to the other to indicate that a shared resource is in use. the semaphore provide the hardware context for the atoken passing allocationo method of use assignment. this method uses the state of a semaphore latch as a token indicating that a shared resource is in use. if the left processor needs to use a resource, it requests the token by setting the latch. the processor then verifies that the latch has been set by reading it. if the latch has been set the processor assumes control over the shared resource. if the latch has not been set, the left processor has established that the right processor had set the latch first, has the token and is using the shared resource. the left processor may then either repeatedly query the status of the semaphore, or abandon its request for the token and perform another operation whilst occasionally attempting to gain control of the token through a set and test operation. once the right side has relinquished the token the left side will be able to take control of the shared resource. the semaphore flags are active low. a token is requested by writing a zero to a semaphore latch, and is relinquished again when the same side writes a one to the latch. the eight semaphore flags are located in a separate memory space from the dual-port ram in the m67025e. the address space is accessed by placing a low input on the sem pin (which acts as a chip select for the semaphore flags) and using the other control pins (address, oe and r/w ) as normally used in accessing a standard static ram. each of the flags has a unique address accessed by either side through address pins a0-a2. none of the other address pins has any effect when accessing the semaphores. only data pin d 0 is used when writing to a semaphore. if a low level is written to an unused semaphore location, the flag will be set to zero on that side and to one on the other side (see table 5). the semaphore can now only be modified by the side showing the zero. once a one is writen to this location from the same side, the flag will be set to one for both sides (unless a request is pending from the other side) and the semaphore can then be written to by either side. the effect the side writing a zero to a semaphore location has of locking out the other side is the reason for the use of semaphore logic in interprocessor communication. (a thorough discussion of the use of this feature follows below). a zero written to the semaphore location from the locked-out side will be stored in the semaphore request latch for that side until the semaphore is relinquished by the side having control. when a semaphore flag is read its value is distributed to all data bits so that a flag set at one reads as one in all data bits and a flag set at zero reads as all zeros. the read value is latched into the output register of one side when its semaphore select (sem ) and output enable (oe ) signals go active. this prevents the semaphore changing state in the middle of a read cycle as a result of a write issued by the other side. because of this latch, a repeated read of a semaphore flag in a test loop must cause either signal (sem or oe ) to go inactive, otherwise the output will never change.
m67025e rev. f june 30, 1999 6 the semaphore must use a write/read sequence in order to ensure that no system level conflict will occur. a processor requests access to shared resources by attempting to write a zero to a semaphore location. if the semaphore is already in use, the semaphore request latch will contain a zero, yet the semaphore flag will appear as a one, and the processor will detect this status in the subsequent read (see table 5). for example, assume a processor writes a zero to the left port at a free semaphore location. on a subsequent read, the processor will verify that it has written successfully to that location and will assume control over the resource concerned. if a processor on the right side then attempts to write a zero to the same semaphore flag it will fail, as will be verified by a subsequent read returning a one from the semaphore location on the right side has a read/write sequence been used instead, system conflict problems could have occurred during the interval between the read and write cycles. it must be noted that a failed semaphore request needs to be followed by either repeated reads or by writing a one to the same location. the simple logic diagram for the semaphore flag in figure 2 illusrates the reason for this quite clearly. two semaphore request latches feed into a semaphore flag. the first latch to send a zero to the semaphore flag will force its side of the semaphore flag low and other side high. this status will be maintained until a one is written to the same semaphore request latch. sould a zero be written to the other side's semaphore request latch in the meantime, the semaphore flag will flip over to this second side as soon as a one is written to the first side's request latch. the second side's flag will now stay low until its semaphore request latch is changed to a one. thus, clearly, if a semaphore flag is requested and the processor requesting it no longer requires access to the resource, the entire system can hang up until a one is written to the semaphore request latch concerned. semaphore timing becomes critical when both sides request the same token by attempting to write a zero to it at the same time. semaphore logic is specially conceived to resolve this problem. the logic ensures that only one side will receive the token if simult aneous requests are made. the first side to make a request will receive the token where request do not arrive at the same time. where they do arrive at the same time, the logic will assign the token arbitrarily to one of the ports. it should be noted, however, that semaphores alone do not guarantee that access to a resource is secure. as with any powerful programming technique, errors can be introduced if semaphores are misused or misinterpreted. code integrity is of the utmost performance when semaphores are being used instead of slower, more restrictive hardware-intensive systems. semaphore initialization is not automatic and must therefore be incorporated in the power up initialization procedures. since any semaphore flag containing a zero must be reset to one, initialization should write a one to all request flags from both sides to ensure that they will be available when required. using semaphores - some examples perhaps the simplest application of semaphores is their use as resource markers for the m67025e's dual-port ram. if it is necessary to split the 8 k 16 ram into two 4 k 16 blocks which are to be dedicated to serving either the left or right port at any one time. semaphore 0 can be used to indicate which side is controlling the lower segment of memory and semaphore 1 can be defined as indicating the upper segment of memory. to take control of a resource, in this case the lower 4 k of a dual-port ram, the left port processor would then write a zero into semaphore flag 0 and then read it back. if successful in taking the token (reading back a zero rather than a one), the left processor could then take control of the lower 4 k of ram. if the right processor attempts to perform the same function to take control of the resource after the left processor has already done so, it will read back a one in response to the attempted write of a zero into semaphore 0. at this point the software may choose to attempt to gain control of the second 4 k segment of ram by writing and then reading a zero in semaphore 1. if successful, it will lock out the left processor. once the left side has completed its task it will write a one to semaphore 0 and may then attempt to access semaphore 1. if semaphore 1 is still occupied by the right side, the left side may abandon its semaphore request and perform other operations until it is able to write and then read a zero in semaphore 1. if the right processor performs the same operation with semaphore 0, this protocol would then allow the two processes to swap 4 k blocks of dual-port ram between one another. the blocks do not have to be any particular size, and may even be of variable size depending on the complexity of the software using the semaphore flags. all eight semaphores could be used to divide the dual-port ram or other shared resources into eight parts. semaphores can even be assigned different meanings on each side, rather than having a common meaning as is described in the above example. semaphores are a useful form of arbitration in systems such as disk interfaces where the cpu must be locked out of a segment of memory during a data transfer operation, and the i/0 device cannot tolerate any wait states. if semaphores are used, both the cpu and the i/0 device can access assigned memory segments, without the need for wait states, once the two devices have determined which memory area is barred to the cpu.
m67025e rev. f june 30, 1999 7 semaphores are also useful in applications where no memory wait state is available on one or both sides. on a semaphore handshake has been performed, both processors can access their assigned ram segments at full speed. another application is in complex data structures. block arbitration is very important in this case, since one processor may be responsible for building and updating a data structure whilst the other processor reads and interprets it. a major error condition may be created if the interpreting processor reads an incomplete data structure. some sort of arbitration between the two different processors is therefore necessary. the building processor requests access to the block, locks it and is then able to enter the block to update the data structure. once the update is completed the data structure may be released. this allows the interpreting processor, to return to read the complete data structure, thus ensuring a consistent data structure. truth table table 1 : non contention read/write control. inputs (1) outputs mode cs r/w oe ub lb sem io 8 io 15 i/o 0 i/o 7 mode h x x x x h hiz hiz deselected : power down x x x h h h hiz hiz deselected : power down l l x l h h data in hiz write to upper byte only l l x h l h hiz data in write to lower byte only l l x l l h data in data in write to both bytes l h l l h h data out hiz read upper byte only l h l h l h hiz data out read lower byte only l h l l l h data out data out read both bytes x x h x x x hiz hiz outputs disabled h h l x x l data out data out read data in sema. flag x h l h h l data out data out read data in sema. flag h x x x l data in data in write d in0 into sema. flag x x h h l data in data in write d in0 into sema. flag l x x l x l not allowed l x x x l l not allowed note : 1. a 0l a 12l a 0r a 12r . table 2 : arbitration options. options inputs outputs options cs ub lb m/s sem busy int busy logic master l x l h h output yg l l x h h signal busy logic slave l x l l h input yg l l x l h signal interrupt logic l x l x h output pg l l x x h signal semaphore logic* h x x h l h pg h x x l l hiz * inputs signals are for semaphore flags set and test (write and read) operations.
m67025e rev. f june 30, 1999 8 table 3 : interrupt flag (1, 4) . left port right port function r/w l cs l oe l a ol a 12l int l r/w r cs r oe r a or a 12r int r function l l x 1fff x x x x x l (2) set right int r flag x x x x x x l l 1fff h (3) reset right int r flag x x x x l (3) l l x 1ffe x set left int l flag x l l 1ffe h (2) x x x x x reset left int l flag notes : 1. assumes busy l = busy r = h. 2. if busy l = l, then nc. 3. if busy r = l, then nc. 4. h = high, l = low, x = don't care, nc = no change. table 4 : arbitration (2) left port right port flags (1) function cs l a 0l a 12l cs r a 0r a 12r busy l busy r function h x h x h h no contention l any h x h h no contention h x l any h h no contention l a 0r a 12r l a 0l a 12l h h no contention address arbitration with cs low before address match l lv5r l lv5r h l lport wins l rv5l l rv5l l h rport wins l same l same h l arbitration resolved l same l same l h arbitration resolved cs arbitration with address match before cs ll5r = a 0r a 12r ll5r = a 0l a 12l h l lport wins rl5l = a 0r a 12r rl5l = a 0l a12l l h rport wins lw5r = a 0r a12r lw5r = a 0l a 12l h l arbitration resolved lw5r = a 0r a 12r lw5r = a 0l a 12l l h arbitration resolved notes : 1. int flags don't care. 2. x = don't care, l = low, h = high. lv5r = left address valid 5 ns before right address. rv5l = right address valid 5 ns before left address. same = left and right addresses match within 5 ns of each other. ll5r = left cs = low 5 ns before right cs . rl5l = right cs = low 5 ns before left cs . lw5r = left and right cs = low within 5 ns of each other.
m67025e rev. f june 30, 1999 9 table 5 : example semaphore procurement sequence. function d 0 d 15 left d 0 d 15 right status no action 1 1 semaphore free left port writes o0o to semaphore 0 1 left port has semaphore token right port writes o0o to semaphore 0 1 no change. right side has no write access to semaphore left port writes o1o to semaphore 1 0 right port obtains semaphore token left port writes o0o to semaphore 1 0 no change. left port has no write access to semaphore right port writes o1o to semaphore 0 1 left port obtains semaphore token left port writes o1o to semaphore 1 1 semaphore free right port writes o0o to semaphore 1 0 right port has semaphore token right port writes o1o to semaphore 1 1 semaphore free left port writes o0o to semaphore 0 1 left port has semaphore token left port writes o1o to semaphore 1 1 semaphore free note : 1. this table denotes a sequence of events for only one of the 8 semaphores on the m67025e. figure 1. m67025e semaphore logic.
m67025e rev. f june 30, 1999 10 electrical characteristics absolute maximum ratings supply voltage (vcc-gnd) : -0.3 v to 7.0 v . . . . . . . . . . . . . . . . . . . input or output voltage applied : (gnd 0.3 v) to . . . . . . . . . . . . . . . (vcc + 0.3 v) storage temperature : 65 c to +150 c . . . . . . . . . . . . . . . . . . . . . . * notice stresses greater than those listed under absolute maximum ratings may cause permanent damage to the device.this is a stress rating only and functional operation of the device at these or any other conditions above those indicated in the operational sections of this specification is not implied. exposure to absolute maximum rating conditions for extented periods may affect reliability. operating supply voltage operating temperature military v cc = 5 v 10 % 55 c to + 125 c dc parameters parameter description 6702530 6702545 unit value i ccsb (1) standby supply current (both ports ttl level inputs) 10 10 ma max i ccsb1 (2) standby supply current (both ports cmos level inputs) 500 500 m a max i ccop (3) operating supply current (both ports active) 320 260 ma max i ccop1 (4) operating supply current (one port active one port standby) 200 180 ma max notes : 1. cs l = cs r 2.2 v. 2. cs l = cs r vcc 0.2 v. 3. both ports active maximum frequency outputs open oe = vih. 4. one port active (f = fmax) output open one port stand-by ttl or cmos level inputs cs l = cs r 2.2 v.
m67025e rev. f june 30, 1999 11 parameter description m67025e unit value il i/o (5) input/output leakage current 10 m a max vil (6) input low voltage 0.8 v max vih (6) input high voltage 2.2 v min vol (7) output low voltage (i/o 0 i/o 15 ) 0.4 v max voh (7) output high voltage 2.4 v min c in input capacitance 5 pf max c out output capacitance 7 pf max notes : 5. vcc = 5.5 v, vin = gnd to vcc, cs = vih, vout = 0 to vcc. 6. vih max = vcc + 0.3 v, vil min = 0.3 v or 1 v pulse width 50 ns. 7. vcc min, iol = 4 ma, ioh = 4 ma. data-retention mode mhs cmos rams are designed with battery backup in mind. data retention voltage and supply current are guaranteed over temperature. the following rules insure data retention : 1 chip select (cs ) must be held high during data retention ; within v cc to v cc 0.2 v. 2 cs must be kept between v cc 0.2 v and 70 % of v cc during the power up and power down transitions. 3 the ram can begin operation > trc after v cc reaches the minimum operating voltage (4.5 volts). timing parameter ( ) test conditions (9) value unit parameter (max) test conditions (9) v unit icc dr @ vcc dr = 2 v 200 m a notes : 8. cs = v cc , vin = gnd to v cc . 9. t rc = read cycle time.
m67025e rev. f june 30, 1999 12 test conditions (8) ac test conditions input pulse levels : gnd to 3.0 v input rise/fall times : 5 ns input timing reference levels : 1.5 v output reference levels : 1.5 v output load : see figures 2, 3 figure 2. output load. figure 3. output load (for t hz , t lz , t wz , and t ow ).
m67025e rev. f june 30, 1999 13 ac electrical characteristics over the full operating temperature and supply voltage range read cycle parameter m 6702530 m 6702545 unit symbol (4) symbol (5) parameter min. max. min. max. unit tavav r t rc read cycle time 30 45 ns tavqv t aa address access time 30 45 ns telqv t acs chip select access time (3) 30 45 ns tblqv t abe byte enable access time (3) 30 45 ns tglqv t aoe output enable access time 15 25 ns tavqx t oh output hold from address change 3 3 ns telqz t lz output low z time (1, 2) 3 3 ns tehqz t hz output high z time (1, 2) 15 20 ns tpu t pu chip select to power up time (2) 0 0 ns tpd t pd chip disable to power down time (2) 50 50 ns tsop t sop sem flag update pulse (oe or sem ) 15 15 ns notes : 1. transition is measured 500 mv from low or high impedance voltage with load (figures 2 and 3). 2. this parameters is guaranteed but not tested. 3. to access ram cs = v il , ub or lb = v il , sem = v ih . to access semaphore cs = v ih , sem = v il . refer to table 1. 4. std symbol. 5. alt symbol.
m67025e rev. f june 30, 1999 14 timing waveform of read cycle n 1, either side (1, 2, 4) timing waveform of read cycle n 2, either side (1, 3, 5) timing waveform of read cycle n 3, either side (1, 3, 4, 5) notes : 1. r/w is high for read cycles. 2. device is continuously enabled, cs = v il , ub or lb = v il . this waveform cannot be used for semaphore reads. 3. addresses valid prior to or coincident with cs transition low. 4. oe = v il . 5. to access ram, cs = v il , ub or lb = v il , sem = v ih . to access semaphore, cs = v ih , sem = v il . refer to table 1.
m67025e rev. f june 30, 1999 15 ac electrical characteristics over the full operating temperature and supply voltage range write cycle parameter m 6702530 m 6702545 unit symbol (4) symbol (5) parameter min. max. min. max. unit tavav w t wc write cycle time 30 45 ns telwh t sw chip select to end of write (3) 25 40 ns tavwh t aw address valid to end of write 25 40 ns tavwl t as address setup time 0 0 ns twlwh t wp write pulse width 25 35 ns twhax t wr write recovery time 0 0 ns tdvwh t dw data valid to end of write 20 25 ns tghqz t hz output high z time (1, 2) 15 20 ns twhdx t dh data hold time (4) 0 0 ns twlqz t wz write enable to output in high z (1, 2) 15 20 ns twhqx t ow output active from end of write (1, 2, 4) 0 0 ns tswrd t swrd sem flag write to read time 10 10 ns tsps t sps sem flag contention window 10 10 ns notes : 1. transition is measured 500 mv from low or high impedance voltage with load (figures 2 and 3). 2. this parameters is guaranteed but not tested. 3. to access ram cs = v il , ub or lb = v il , sem = v ih . to access semaphore cs = v ih , sem = v il . this condition must be valid for entire t sw time. 4. the specification for t dh must be met by the device supplying write data to the ram under all operating conditions. although t dh and t ow values will vary over voltage and temperature, the actual t dh will always be smaller than the actual t ow . 5. std symbol. 6. alt symbol.
m67025e rev. f june 30, 1999 16 timing waveform of write cycle n 1, r/w controlled timing (1, 2, 3, 7) timing waveform of write cycle n 2, cs controlled timing (1, 2, 3, 5) notes : 1. r/w must be high during all address transitions. 2. a write occurs during the overlap (t sw or t wp ) of a low cs or se m and a low r/w . 3. t wr is measured from the earlier of cs or r/w (or se m or r/w ) going high to the end of write cycle. 4. during this period, the i/o pins are in the output state, and input signals must not be applied. 5. if the cs or sem low transition occurs simultaneously with or after the r/w low transition, the outputs remain in the high imped- ance state. 6. transition is measured 500 mv from steady state with a 5pf load (including scope and jig).this parameter is sampled and not 100 % tested. 7. if oe is low during a r/w controlled write cycle, the write pulse width must be the larger of t wp or (t wz + t dw ) to allow the i/o drivers to turn off and data to be placed on the bus for the required t dw . if oe is high during an r/w controlled write cycle, this requirement does not apply and the write pulse can be as short as the specified t wp . 8. to access ram, cs = v il . sem = v ih . 9. to access upper byte cs = v il , ub = v il , sem = v ih . to access lower byte cs = v il , lb = v il , sem = v ih .
m67025e rev. f june 30, 1999 17 ac electrical characteristics over the full operating temperature and supply voltage range write cycle parameter m 6702530 m 6702545 unit cycle parameter min. max. min. max. unit busy timing (for master 67025 only) t baa busy access time to address 30 35 ns t bda busy disable time to address 25 30 ns t bac busy access time to chip select 25 30 ns t bdc busy disable time to chip select 20 25 ns t wdd write pulse to data delay (1) 55 70 ns t ddd write data valid to read data delay (1) 40 55 ns t aps arbitration priority setup time (2) 5 5 ns t bdd busy disable to valid data note 3 note 3 ns busy timing (for slave 67025 only) t wb write to busy input (4) 0 0 ns t wh write hold after busy (5) 20 25 ns t wdd write pulse to data delay (6) 55 70 ns t ddd write data valid to read data delay (6) 40 55 ns notes : 1. port-to-port delay through ram cells from writing port to reading port, refer to atiming waveform of read with busy (for master 67025 only). 2. to ensure that the earlier of the two ports wins. 3. t bdd is a calculated parameter and is the greater of 0, t wdd t wp (actual) ot t ddd t dw (actual). 4. to ensure that the write cycle is inhibited during contention. 5. to ensure that a write cycle is completed after contention. 6. port-to-port delay through ram cells from writing port to reading port, refer to atiming waveforms of read with port-to-port delay (for slave, 67025 only)o.
m67025e rev. f june 30, 1999 18 timing waveform of read with busy (2, 3, 4) (for master 67025) notes : 1. to ensure that the earlier of the two port wins. 2. write cycle parameters should be adhered to, to ensure proper writing. 3. device is continuously enabled for both ports. 4. oe = l for the reading port. timing waveform of write with port-to-port (1, 2, 3) (for slave 67025 only) notes : 1. assume busy = h for the writing port, and oe = l for the reading port. 2. write cycle parameters should be adhered to, to ensure proper writing. 3. device is continuously enabled for both ports.
m67025e rev. f june 30, 1999 19 timing waveform of write with busy (for slave 67025) timing waveform of contention cycle n 1, cs arbitration (for master 67025 only)
m67025e rev. f june 30, 1999 20 timing waveform of contention cycle n 2, address valid arbitration (for master 67025 only) (1) left address valid first : right address valid first : note : 1. cs l = cs r = v il ac parameters interrupt timing parameter 6702530 6702545 unit symbol parameter min. max. min. max. unit t as address setup time 0 0 ns t wr write recovery time 0 0 ns t ins interrupt set time 25 35 ns t inr interrupt reset time 25 35 ns
m67025e rev. f june 30, 1999 21 waveform of interrupt timing (1) notes : 1. all timing is the same for left and right ports. port aao may bei either the left or right port. port abo is the port opposit e from aao. 2. see interrupt truth table. 3. timing depends on which enable signal is asserted last. 4. timing depends on which enable signal is de-asserted first. 32-bit master/slave dual-port memory systems notes : 1. no arbitration in m67025e (slave). busy -in inhibits write in m67025e slave.
m67025e rev. f june 30, 1999 22 timing waveform of semaphore read after write timing, either side (1) note : 1. cs = v ih for the duration of the above timing (both write and read cycle). timing waveform of semaphore contention (1, 3, 4) notes : 1. d or = d ol = v il , cs r = cs l = v ih , semaphore flag is released from both sides (reads as ones from both sides) at cycle start. 2. either side aao = left and side abo = right, or side aao = right and side abo = left. 3. this parameter is measured from the point where r/w a or sem a goes high until r/w b or sem b goes high. 4. if t sps is violated, the semaphore will fall positively to one side or the other, but there is no guaranted which side will obtain the flag.
m67025e rev. f june 30, 1999 23 ordering information m = military 55 to +125 c s = space 55 to +125 c k2 = 84 pins mqfpf* 0 = dice form 8k 16 dual port ram m 67025ev c k2 30 30 ns 45 ns temperature range package device speed flow m = 5 v version v = very low power * 50 mils pitch blank = mhs standards /883 = mil std 883 class b or s sb/sc = scc 9000 level b/c qm = qmlq sv = qmlv the information contained herein is subject to change without notice. no responsibility is assumed by temic for using this publ ication and/or circuits described herein : nor for any possible infringements of patents or other rights of third parties which may result from its use .

▲Up To Search▲

Price & Availability of MMK2-67025EV-45QM

	To Download MMK2-67025EV-45QM Datasheet File
If you can't view the Datasheet, Please click here to try to view without PDF Reader .